Constructing a Distributed Developing Environment Using Epics for Bepcii Control System

Probe: to debug database records. • Alarm handler ALH The current Beijing Electron Position Collider (BEPC) is going to be upgraded to reach a higher energy as 1.89 GeV and a luminosity of 1.0E33cms. A second storage ring will be installed in the same tunnel of BEPC. The control system of BEPCII will be constructed based on EPICS. During the past two years a basic prototype has been set up, including 2 Solaris workstations, a Linux PC and MVME2431 CPU boards. EPICS 3.13.4 has been installed and upgraded to 3.13.8. Upon this scalable prototype a distributed computing environment is under construction, to support the commissioning software development and kinds of subsystem development. The efforts of setting up the EPICS based prototype will be introduced in this paper. The methods of constructing a distributed host environment for BEPCII control system will be discussed. Figure 1: Application using Striptool Besides EPICS, some third-party software have been installed [4], either to support the compiling and linking of EPICS, or to enlarge the ability of OPI for the system, such as Python, Tcl/Tk and Gnuplot. Figure 2 shows an example using Gnuplot to display the data archived by Channel Archiver from the running of excas. INTRODUCTION The Beijing Electron-Position Collider (BEPC) was constructed for both high energy physics and synchrotron radiation researches. The BEPC accelerators consist of a 202-meter’s long electron-position linac injector, a storage ring with a circumference of 240.0 meters, and transport lines with the total length of 210 meters. [1] BEPCII is an upgrade project of BEPC aiming at the luminosity of 1×10cms at 1.89 GeV. It consists of 2 rings with electron and position circulating in each separate storage ring while colliding at the common interaction point. The two rings are accommodated in the existing BEPC tunnel. [2] The control system of BEPCII will be constructed using EPICS and adopt a distributed architecture. [3] EPICS FOR BEPCII Figure 2: Example of using Gnuplot In 2001 a mini EPICS environment was set up for the preliminary design of BEPCII. That environment included a Solaris workstation Ultra-10, MVME 2431. EPICS base 3.13.4 and vxWorks 5.4.2 were chosen. The original Solaris 2.6 was upgraded to Solaris 2.8 in the summer of 2002. Compiling Extensions Some parameters in makefiles have been re-configured while compiling the extensions, to specify the location of kinds of libraries in our system, tools used, versions of tools, and so on. Tools Built • For dm2k and MEDM, parameters in the makefiles have been set to use JPT, instead of XRT or SciPlot. EPICS base 3.13.4 and most of the extensions have been compiled. Simple applications have been built to practise some of the often-used tools, such as: • Some commercial software packages such as XPM and Pure have not been bought in our group so the lines for using these tools in the makefiles have been commented out • MEDM, dm2k and EDM. All of these tools are welcome and EDM is more preferred in our group. • Database configuration tools VDCT and Capfast. • Small patches were made to compile Channel Archiver in Solaris 2.8. • Striptool. Figure 1 shows a example using Striptool. Proceedings of ICALEPCS2003, Gyeongju, Korea